Refactor to use new batch context varaibles #967
Merged
+9
−3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
resolves #966
Problem
During the betas/rcs of dbt-core 1.9.0, the varaibles
__dbt_internal_event_time_start
and__dbt_internal_event_time_end
were available on the model in the jinja context. However when the final of dbt-core 1.9.0 was released, dbt-core started providing abatch
object on the model available in the jinja context. This batch object made availble all the prevous information and more, and it is the "correct" way to get the information (i.e.__dbt_internal_event_time_end
and__dbt_internal_event_time_start
are deprecated.Solution
Update the microbatch incremental strategies to use
model.batch.<variable>
variablesChecklist